Outlook 2003 Scheduling Problem - One User shows "No Information"
We are currently running Exchange 2007 (Single Server Install) and Outlook 2003 on our workstations. This is only occurring with one user at the moment. When trying to schedule a meeting, one of our user's schedule shows up as "No Information". The other users show their availability without a problem. If I attempt to schedule a meeting for this user using OWA or Outlook 2007, the correct free/busy information shows up just fine. Any input would be greatly appreciated.Thanks!
March 24th, 2009 6:19pm

The user that is having the issue, have them run outlook.exe /cleanfreebusy . Also is this a new user? I've seen it with a new user and once someone puts something on the calendar it initializes it or something similar. Mark Morowczynski|MCSE 2003:Messaging, Security|MCITP: Enterprise Support|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2009 7:29pm

This is not a new user and in the past their calendar free/busy has been viewable. Their free/busy information IS viewable if I access it from OWA or Outlook 2007. Any other suggestions would be helpful.Thanks!
March 24th, 2009 8:49pm

Did you try having that user run outlook.exe /cleanfreebusy Mark Morowczynski|MCSE 2003:Messaging, Security|MCITP: Enterprise Support|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2009 9:54pm

Yes I had them run the outlook.exe /cleanfreebusy flag and we are still seeing the same issue of "No Information" for that users calendar under scheduling. Any other ideas would be helpful!Thanks!
March 24th, 2009 11:02pm

Issue description: Single users free/busy [FB] info cannot be seen by other users, showed as No Information Explanation: Outlook 2007 retrieve others Free/Busy information by querying the others calendar folder directly through AS (Availability Service). Outlook 2003 retrieve others Free/Busy by querying the information from the Free/Busy system folder in the Public Folder store Check info: 1. I assume it is a pure exchange 2007 environment with a single exchange 2007 server (MBX, CAS, HUB), please correct me if Ive misunderstood it 2. Do all outlook 2003 users cannot see problematic users FB info? 3. Had the problematic user modified the alias before? Had the problematic users mailbox been moved before Troubleshooting: 1. Please verify problematic users legacyExchangeDN attribute via ADSI Editor (KB 286783) 2. Please check the public folder store in the replica list of the folder under "Schedule+ Free/Busy" public folder via Public Folder Management Console (PFMC) 3. Please check the default public folder database in the mailbox store (Method) 4. Please use MAPI Editor to verify if the FB message of problematic user exists a. Launch MAPI Editor on a client PC which has mail profile set b. Session menu->choose Logon and Display Store Table->choose profile in jumped window c. Choose Public folder from upper window->enter the users credential in jumped window d. In the next window, expand Public root->NON_IPM_SUBTREE->double-click the folder under Schedule+ Free/Busy (EX:/o=OrganizationName/ou=AdministrativeGroupName) e. Search problematic users FB message by the Subject column, the format is USER-/CN=RECIPIENTS/CN= AliasOfUser Notes: If there are duplicate FB messages for the problematic user, delete the oldest ones and leave the newest one 5. Please verify the delivery location on the problematic users outlook client (KB 831234) 6. If all above is normal, please remove problematic users FB message in the MAPI Editor and republish the message on the problematic users outlook by using switch /cleanfreebusy. After you see that message is being regenerated via MAPI Editor, please check the issue again Resources: Effects on Free/Busy Data When Moving or Deleting Users' Mailboxes
Free Windows Admin Tool Kit Click here and download it now
March 26th, 2009 10:33am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics